Fix/cleanup destroyDevice code path in xend.
authorkfraser@localhost.localdomain <kfraser@localhost.localdomain>
Mon, 6 Aug 2007 09:12:34 +0000 (10:12 +0100)
committerkfraser@localhost.localdomain <kfraser@localhost.localdomain>
Mon, 6 Aug 2007 09:12:34 +0000 (10:12 +0100)
commite080ffba8d9368b57e4b9a882f7c9729efe9f9db
tree86491b80cb7b06fe7cc76c90ee0587d96d313b21
parent883ff6165736e4ac0511245fd76f1645d10bdde4
Fix/cleanup destroyDevice code path in xend.

When calling destroyDevice code path (e.g. xm block-detach dom devid),
allow specifying an integer device id or a device name such as xvdN or
/dev/xvdN.  Allowing the /dev/xvdN form is useful when detaching
devices from dom0.  Bootloaders may do this to unmount a disk
previously mounted in dom0.

Move examination of device ID format into the DevController,
permitting device controllers to determine a valid device ID instead
of higher level code.

Signed-off-by: Jim Fehlig <jfehlig@novell.com>
tools/python/xen/xend/XendDomainInfo.py
tools/python/xen/xend/server/DevController.py
tools/python/xen/xend/server/blkif.py
tools/security/policies/default-security_policy.xml [new file with mode: 0644]
tools/security/policies/default-ul-security_policy.xml [new file with mode: 0644]